- 5 minutes to read

PowerShell

Nodinite enables you to monitor, automate, and empower users with custom PowerShell scripts on your Windows Servers. With this feature, you can run scripts for advanced monitoring, automate routine tasks, and provide secure self-service actions for end-users—all from a single, unified platform.

✅ Execute virtually any PowerShell script for custom monitoring and automation
✅ Empower end-users to run scripts as Remote Actions on demand
✅ Centralize script management and execution for security and compliance

Info

Learn how to utilize your own PowerShell scripts for custom monitoring, enabling end-users to execute them through self-service enabled Nodinite Monitor Views.

graph LR subgraph "fal:fa-rectangle-terminal Nodinite " roNI[fal:fa-monitor-waveform Windows Server Monitoring Agent] --- |Local execution| roSRV1[fal:fa-server Server A] end subgraph "Other network" roNI --- |Remote execution| roSRV2[fal:fa-server Server B] end

This diagram illustrates how Nodinite executes PowerShell scripts both locally and remotely, enabling flexible monitoring and automation across your infrastructure.

Note

⚠️ You must have WMF 5.1 or later.
⚠️ WinRM must be enabled on remote Windows Server if you are using the PowerShell feature with a remote target.

This page outlines how Nodinite monitors the PowerShell Category using one or more role-based Monitor Views. You can configure state evaluation based on user-defined logic—globally or for specific scripts. Remote commands (Actions) are available to help you swiftly address reported problems. All implemented Remote Actions are detailed below.

PowerShell items as Resources
Example list of monitored 'PowerShell' resources in a Monitor View.

Monitoring Features

  • Administrators manually manage your PowerShell configurations. Sharing insights is easy with Monitor Views.
  • State Evaluation – Based on script output: Write-Warning for Warnings, Write-Error for Errors.
  • Category-based monitoring – Group monitored Resources by Categories for streamlined management.

State evaluation for PowerShell-based monitoring

Nodinite displays each monitored PowerShell configuration as a Resources. For example, if you have 2 Windows Server configurations with 2 and 3 PowerShell scripts, you will have 5 'PowerShell' resources in Nodinite.

  • The Resources name matches the name of the PowerShell configuration.

  • The 'PowerShell' resource belongs to the following Category:

    Category Description
    PowerShell Ensure PowerShell configurations stay within user-defined monitoring thresholds

    Categories
    List of PowerShell-related resources in a Monitor View.

  • The Application name is the Display Name of the Windows Server:
    Application Path Naming Example
    Example using the Application filter option in a Nodinite Monitor View.

Each item (presented in Nodinite as a Resource) is evaluated with a state: OK, Warning, Error, or Unavailable.

You can reconfigure state evaluation at the Resources level using the Expected State feature.

Note

Depending on the user-defined synchronization interval for the Windows Server Monitoring Agent, there may be a delay before Nodinite Web Client/Monitor Views reflect changes. Click Sync All (or use the dropdown for individual agent selection) to force a resynchronization.

Sync option
Option to force Nodinite to request a resynchronization with the Monitoring Agent.

PowerShell Monitoring

For the PowerShell category, Nodinite evaluates the monitored state as described below:

State Status Description Actions
Unavailable Service not available The server can't be reached or evaluated due to network or security issues Review prerequisites
Error Error state raised The script fails or contains Write-Error in the output Details
Show Action Scripts
Warning Warning state raised The script failed or contains Write-Warning in the output Details
Show Action Scripts
OK Operational The 'PowerShell' configuration is valid, and the script executes without any errors or warnings Details
Show Action Scripts

Remote Actions for PowerShell

The following Remote Actions are available for the PowerShell Category:

PowerShell Remote Actions
Available remote actions for the PowerShell category.

Details

View details for any PowerShell resource by clicking the Action button and selecting Details in the 'Control Center' section.

Details Menu Action
Open details modal using the 'Details' action.

Next, click the option to open the modal.

Details Modal
Example of the 'Details' modal.

Show Action Scripts

Manage and execute scripts for any PowerShell resource by clicking the Action button and selecting Show Action Scripts in the 'Control Center' section.

Show Action Scripts Action
Open the scripts modal using the 'Show Action Scripts' action.

Next, click the option to open the modal.

Show Action Scripts Modal
Example of the 'Action Scripts' modal.

Click the Execute button to run the script on demand.

Confirm intent
The user must confirm the intent to execute the script.

The output is presented at the bottom of the modal.

PowerShell Script Output
Example of the result from the operation.

Configuration

Use Remote Configuration to manage PowerShell configuration.

PowerShell tab

Click the PowerShell tab to manage PowerShell monitoring options.
PowerShell tab
Example of the 'PowerShell' configuration tab.

State Example code Description
OK echo "Hello World" Script runs without errors and has no warnings or errors written to the output
Warning Write-Warning "Warning for moderate rain" Script runs without errors and has a warning written to the output
Error Write-Error "General failure reading from disk" Script fails or has errors written to the output

Click the Add button to add a new entry. This will become the Resource as seen in Monitor Views.

PowerShell General tab

This is the monitoring entry.

  • Enabled – When checked, this PowerShell Script is monitored
  • Display Name – The user-friendly name of this resource as provided to end-users within Monitor Views
  • Description – User-friendly description for the PowerShell Script resource
  • PowerShell Script – The script to use for monitoring
    PowerShell General tab
    Example of the PowerShell configuration General tab.

User Action Scripts

This entry allows the System Administrator to provide a script collection for end-users with permission to execute content as Remote Actions.
PowerShell User Script Collection tab
Example of the PowerShell User Script Collection tab.

Click the Add button for each script to include in the script collection.
User script entry
Example of a PowerShell User Script entry.

PowerShell Authentication

Set authentication options for executing the PowerShell script.
Authentication tab
Example of the PowerShell configuration Authentication tab.

Check the checkbox to execute the script on another target host.

  • Is remote server – When checked, these PowerShell Scripts run on a remote server.
    • Address – The address for the remote server.
  • Use authentication – When checked, authenticate to the remote server or impersonate a user locally via the username and password fields below.
    • Domain User – The name of the Windows user account. Format: DOMAIN\User.
    • Password – The password for the provided domain user.

Authentication fields
Example of the PowerShell configuration Authentication fields.

Next Step

Add or manage Monitor View

Windows Server Monitoring Agent
Resources
Monitoring
Monitor Views